- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1
Feedback from tomogram picking #682
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| Codecov Report❌ Patch coverage is  Additional details and impacted files@@            Coverage Diff             @@
##             main     #682      +/-   ##
==========================================
+ Coverage   35.26%   35.77%   +0.50%     
==========================================
  Files          91       92       +1     
  Lines       11225    11308      +83     
  Branches     1487     1495       +8     
==========================================
+ Hits         3959     4045      +86     
+ Misses       7138     7130       -8     
- Partials      128      133       +5     🚀 New features to boost your workflow:
 | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Doesn't seem to be anything obviously wrong. Feel free to merge once you're happy with it!
Ability to receive messages back from tomogram picking and then send on a request to run tomogram 2d extraction/classification.
SPAFeedbackParametersto a more generalClassificationFeedbackParametersfor reuseCurrently then set to run 2D classification in batches of 10000 particles with 5 classes. Needs deciding if that is the right value.
Also probably isn't sending exactly the right set of parameters onwards to the next recipe as the recipe hasn't yet been written, but the right items should be stored in the database here.